{ }
A California man, Ken Liem, has filed a lawsuit against Fubon Bank, Chong Hing Bank, and DBS Bank, claiming they facilitated a $1 million cryptocurrency scam by failing to conduct essential compliance checks, including KYC and AML measures. The lawsuit alleges that these banks overlooked suspicious activities linked to accounts that funneled Liem's funds to scammers, potentially violating the US Bank Secrecy Act. This case underscores the growing vulnerabilities in the financial system regarding cross-border crypto fraud and the responsibilities of banks in preventing such scams.
California resident Ken Liem is suing three Asia-based banks for nearly $1 million, claiming they failed to prevent a pig butchering cryptocurrency scam that began with a LinkedIn investment offer in June 2023. His attorneys allege that funds were transferred to accounts at Fubon Bank, Chong Hing Bank, and DBS Bank, which were then funneled to third-party accounts. Meanwhile, the DeFi market is seeing significant activity, with Solana's price rebounding above $200 and Aave's net deposits reaching a record $33.4 billion.
Trending
Subcategory:
Countries:
Companies:
Currencies:
People:

Machinary offers a groundbreaking, modular, and customizable solution that provides advanced financial news and statistical analysis. Our platform goes beyond traditional quantitative analysis, offering users a comprehensive understanding of real-time market dynamics, event detection, and risk analysis.

Address

Newsletter

© 2025 by Machinary.com - Version: 1.0.0.0. All rights reserved

Layout

Color mode

Theme mode

Layout settings

Seems like the connection with the server has been lost. It can be due to poor or broken network. Please hang on while we're trying to reconnect...
Oh snap! Failed to reconnect with the server. This is typically caused by a longer network outage, or if the server has been taken down. You can try to reconnect, but if that does not work, you need to reload the page.
Oh man! The server rejected the attempt to reconnect. The only option now is to reload the page, but be prepared that it won't work, since this is typically caused by a failure on the server.